feat(skills): add Terramate migration reference to atmos-migration - #2871
feat(skills): add Terramate migration reference to atmos-migration#2871Erik Osterman (Cloud Posse) (osterman) wants to merge 2 commits into
Conversation
Extends the atmos-migration agent skill with a construct-by-construct
mapping from Terramate (stack.tm.hcl, globals, generate_hcl,
script{} orchestration, tags/labels, tm_* functions, Terramate Cloud
sync, .tmtriggers) to Atmos stack configuration, wired into the
skill's routing table and resource list.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
Tip Atmos Pro
No affected stacks workflow was detected for this pull request. 
|
Erik Osterman (Cloud Posse) (osterman)
added
the
no-release
…gration-skill # Conflicts: # agent-skills/skills/atmos-migration/SKILL.md
|
Warning Review limit reached
Next review available in: 43 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Dependency Review✅ No vulnerabilities or license issues found.Scanned FilesNone |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2871 +/- ##
==========================================
- Coverage 82.75% 82.75% -0.01%
==========================================
Files 1860 1860
Lines 180337 180337
==========================================
- Hits 149240 149236 -4
- Misses 23309 23314 +5
+ Partials 7788 7787 -1
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
1 participant
what
references/from-terramate.mdreference file to theatmos-migrationagent skill, giving a construct-by-construct mapping from a Terramate project to Atmos:stack.tm.hcl, hierarchicalglobals,generate_hclmixins/generators,script{}orchestration, tags/labels,tm_*functions, Terramate Cloud sync, the_bootstrap/two-phase pattern, and.tmtriggers/.atmos-migration/SKILL.md's frontmatter, "Decide the Migration Shape First" routing table, and "Additional Resources" section, following the same pattern already used for native-Terraform and Terraform-Workspaces migrations.atmos-migrationrow inagent-skills/AGENTS.md's skill index to mention Terramate.metadata.tags/metadata.labelssyntax,--tags/--labelsCLI filtering, and--include-dependencies/--include-dependentsclosure selection, and flags the one remaining gap: no Atmos equivalent to Terramate's.tmtriggers/change-detection overrides.why
atmos-migrationskill for native Terraform and Terraform Workspaces (and explicitly calls out Terragrunt as unsupported); Terramate was the next common migration source with no guidance, so this extends the existing pattern rather than introducing a new skill.references